Data Processing System and Method for Managing Enterprise Information

ABSTRACT

A method for enterprise information management includes receiving first input information, from a first user, that corresponds to a first identifying a first feature of an organization. The method further includes generating, using the input information, a first data object that represents the first feature of the organization. The method further includes generating a second data object based on second input information. The method further includes hierarchically associating the second data object with the first data object using the first input information and the second input information. The method further includes generating output information, in response to a second user accessing the first data object, based on the first data object, the second data object, and contact information associated with the second user. The method further includes displaying the output information on a display.

TECHNICAL FIELD

This disclosure relates to data processing systems and methods formanaging enterprise information.

BACKGROUND

An enterprise information management office may manage asset andliability information for an organization. For example, an enterpriseinformation management office may include a family office which mayprovide: asset management; family governance management; propertymanagement; art, yacht, and aircraft management; reporting; insuranceplanning; risk management; trust and partnership administration; recordkeeping; tax returns and projections; coordinate estate planning andother legal matters; philanthropy management; personal security;reputational risk; family education; and/or travel, meetings, events,and concierge services; for a family. For example, a single familyoffice may provide asset and trust management services for a singlefamily over multiple generations of the family.

Enterprise information management offices may utilize various disparateand disconnected technologies to manage day-to-day operations of assetsand liabilities associated with an organization utilizing the enterpriseinformation management office. For example, a family office may rely onemail, spreadsheets, calendars, and/or other disconnected technologiesfor managing obligations, both legal and customer oriented, of a familyassociated with the family office. This may result in excess overhead,work inefficiency, and/or an inability of professionals operating withinthe family office to meet the obligations of the family.

SUMMARY

This disclosure relates generally to enterprise information management.

An aspect of the disclosed embodiments is a method for enterpriseinformation management. The method includes receiving, at a servercomputing device, first input information, from a first user using aclient computing device, that corresponds to a first identifying a firstfeature of an organization. The method further includes generating, bythe server computing device and using the input information, a firstdata object that represents the first feature of the organization. Themethod further includes generating, by the server computing device, asecond data object based on second input information. The method furtherincludes hierarchically associating, by the server computing device, thesecond data object with the first data object using the first inputinformation and the second input information. The method furtherincludes storing, by the server computing device, a relationship betweenthe first data object and the second data object in a first database.The method further includes generating, by the server computing deviceoutput information, in response to a second user accessing the firstdata object, based on the first data object, the second data object, andcontact information associated with the second user and retrieved from asecond database separate from the first database, wherein the outputinformation includes a subset of information indicated by the first dataobject and the second data object, the subset of information beingdetermined based on access rights indicated by the contact information.The method further includes displaying, on the client computing device,the output information on a display.

Another aspect of the disclosed embodiments is a system for enterpriseinformation management. The system includes a memory and a processor,wherein the memory includes instructions executable by the processor to:receive first input information, from a first user, that corresponds toa first identifying a first feature of an organization; generate, usingthe input information, a first data object that represents the firstfeature of the organization; generate a second data object based onsecond input information; hierarchically associate the second dataobject with the first data object using the first input information andthe second input information; storing a relationship between the firstdata object and the second data object in a first database; generatingoutput information, in response to a second user accessing the firstdata object, based on the first data object, the second data object, andcontact information associated with the second user and retrieved from asecond database separate from the first database, wherein the outputinformation includes a subset of information indicated by the first dataobject and the second data object, the subset of information beingdetermined based on access rights indicated by the contact information;and display the output information on a display.

Another aspect of the disclosed embodiments is a non-transitorycomputer-readable storage medium, comprising executable instructionsthat, when executed by a processor, facilitate performance ofoperations, comprising: receiving first input information, from a firstuser, that corresponds to a first identifying a first feature of anorganization; generating, using the input information, a first dataobject that represents the first feature of the organization; generatinga second data object based on second input information; hierarchicallyassociating the second data object with the first data object using thefirst input information and the second input information; storing arelationship between the first data object and the second data object ina first database; generating output information, in response to a seconduser accessing the first data object, based on the first data object,the second data object, and contact information associated with thesecond user and retrieved from a second database separate from the firstdatabase, wherein the output information includes a subset ofinformation indicated by the first data object and the second dataobject, the subset of information being determined based on accessrights indicated by the contact information; and displaying the outputinformation on a display.

These and other aspects of the present disclosure are disclosed in thefollowing detailed description of the embodiments, the appended claimsand the accompanying figures.

BRIEF DESCRIPTION OF DRAWINGS

The disclosure is best understood from the following detaileddescription when read in conjunction with the accompanying drawings. Itis emphasized that, according to common practice, the various featuresof the drawings are not to-scale. On the contrary, the dimensions of thevarious features are arbitrarily expanded or reduced for clarity.

FIG. 1 is a block diagram of an example of an electronic computing andcommunications system.

FIG. 2 is a block diagram of an example internal configuration of acomputing device of the electronic computing and communication systemshown in FIG. 1.

FIG. 3 generally illustrates an output interface according to theprinciples of the present disclosure.

FIG. 4 generally illustrates a user control page according to theprinciples of the present disclosure.

FIG. 5 generally illustrates a collection dashboard according to theprinciples of the present disclosure.

FIG. 6 generally illustrates linked smart data objects according to theprinciples of the present disclosure.

FIGS. 7-27 generally illustrates an example case study according to theprinciples of the present disclosure.

FIG. 28 is a flow diagram of a process for managing enterpriseinformation according to the principles of the present disclosure.

DETAILED DESCRIPTION

An enterprise information management office may provide enterpriseinformation management to an organization. An enterprise informationmanagement office may include a family office (e.g., a single familyoffice (SFO) or a multi-family office (MFO)). A family office mayprovide management services to a family utilizing the family office.Management services may include managing enterprise information.Managing enterprise information may include, but is not limited to:asset management; family governance management; property management;reporting; insurance planning; risk management; trust and partnershipadministration; record keeping; tax returns and projections; coordinateestate planning and other legal matters; philanthropy management;personal security; reputational risk; family education; and/or travel,meetings, events, and concierge services; for a relatively wealthyfamily. For example, an SFO may provide asset and trust managementservices for a wealthy family and may operate to provide management ofenterprise information across multiple generations of a wealthy family.

Typically, the enterprise information management office participates inday-to-day activities of the organization the enterprise informationmanagement office represents. For example, a family office participatesin day-to-day activities of a family's controlled businesses and/orassets.

Complexity managing the day-to-day activities has long been the primarycharacteristic of the enterprise information management officeinfrastructure, and experienced professionals have long been required tosuccessfully navigate this complexity using time honored fiduciaryprinciples and practices. As a result of: more regulation; threats oflegal and tax challenges; the global expansion and diversity oforganizational members, asset classes, entity structures, andjurisdictional choices, the complexity of the day-to-day operations ofan enterprise information management office has increase. Additionally,stakeholders are more engaged and seek greater transparency andaccountability for the integrity of enterprise information managementoffice systems of internal controls that support decisions andgovernance.

Typically, enterprise information management office functions thatsupport governance, operations, reporting, and compliance have relied onemail, manual processes, generic calendar applications, spreadsheets,and various combinations thereof, which has created a technology voidfor enterprise information management offices, and in particular, tofamily office functions. This technology void has resulted in slow,inefficient, and sometimes, inaccurate or incomplete work product.Accordingly, a system that is configured to close this technology gapand improve efficiency, speed, accuracy, and other aspects of anenterprise information management office, such as the enterpriseinformation management system 1000, as is generally illustrated in FIG.1, may be advantageous.

In some embodiments, an enterprise information management system (“EIMsystem”), according to the principles of the present disclosure, may beused by an enterprise information management office, such as a familyoffice, to manage information, such as, documents, tasks, calendars,emails and other communications, tax information, legal obligations,other suitable information, or a combination thereof. The EIM system mayinclude one or more databases, one or more application programinterfaces (API), a web based front end, and/or a backend platform. TheEIM system may comprise various systems, such as computing systems,cloud based systems, Internet based systems, and/or other suitablesystems. For example, the EIM system may utilize REST APIs (which maysend and receive JSON objects), GO platform systems, JavaScript, and/orSQL database systems. The principles of the present disclosure describedherein may be implemented in one or more computing systems, such as thesystems described in FIGS. 1 and 2, or other suitable computing systems.In some embodiments, databases, such as PostgreSQL databases, associatedwith the EIM system may store encrypted documents, non-encrypteddocuments, other suitable documents, and/or a combination thereof. TheEIM system, according to the principles of the present disclosure, isconfigured to solve the aforementioned technological problems facingenterprise information management offices, such as, family offices. TheEIM system digitally introduces control to the complexity of familyoffice operations, reporting and compliance which leads to improvedefficiencies and risk mitigation. Architecture associated with the EIMsystem is adapted and/or configured to meet the unique technologyrequirements of an enterprise information management office, such as, afamily office. Every feature of an organization, which includes, but isnot limited to, organizational member, entity, person, object, asset,and/or liability, can be separately managed within its own collaborativeenvironment. Additionally, or alternatively, every organizationalmember, entity, asset, and/or liability may be governed by a unique setof data rules for its interactions and transactions and its ownparticipants subject to a sophisticated user access system adapted tosupport all required roles from executive governance to mail clerks.

FIG. 1 is a block diagram of an example of an enterprise informationmanagement system (“EIM” system) 1000 in accordance with thisdisclosure. The EIM system 1000 may include an electronic computing andcommunications system. As used herein, the term electronic computing andcommunications system, and EIM system, or variations thereof, can be, orinclude, a distributed computing system (e.g., a client-server computingsystem), a cloud computing system, a clustered computing system, or thelike.

The system 1000 can include one or more users 1002. A user 1002 mayinclude a professional performing one or more operations or functions insupport of an enterprise information management office that utilizes thesystem 1000. For example, a user 1002 may include an estate planningattorney performing estate planning functions of a family office usingthe system 1000. The user 1002 can include one or more clients. Forexample, and without limitation, the user 1002 can include a client1004. The client 1004 can comprise a computing system, which can includeone or more computing devices, such as a mobile phone, a tabletcomputer, a laptop computer, a notebook computer, a desktop computer, orany other suitable computing device or combination of computing devices.In some implementations, the client 1004 can be implemented as a singlephysical unit or a combination of physical units. In someimplementations, a single physical unit can include multiple clients.

In some implementations, the client 1004 can be an instance of anapplication running on a user device associated with the user 1002. Asused herein, the term “application” can include, but is not limited to,applications, programs, instances, processes, threads, services,plugins, patches, application version upgrades, or any otheridentifiable computing unit. The system 1000 can include any number ofusers or clients or can have a configuration of users or clientsdifferent from that generally illustrated in FIG. 1. For example, andwithout limitation, the system 1000 can include hundreds or thousands ofusers and at least some of the users can include or be associated withany number of clients. A user can include a user network or domain. Forexample, and without limitation, the client 1004 can be associated orcommunicate with a user network or domain.

The system 1000 can include a datacenter 1008. The datacenter 1008 caninclude one or more servers. For example, and without limitation, thedatacenter 1008, as generally illustrated, includes an applicationserver 1012 and a database server 1016. A datacenter, such as thedatacenter 1008, can represent a geographic location, which can includea facility, where the one or more servers are located. The system 1000can include any number of datacenters and servers or can include aconfiguration of datacenters and servers different from that generallyillustrated in FIG. 1. For example, and without limitation, the system1000 can include tens of datacenters, and at least some of thedatacenters can include hundreds or any suitable number of servers. Insome implementations, the datacenter 1008 can be associated orcommunicate with one or more datacenter networks or domains, which caninclude domains other than the client domain.

In some implementations, the client 1004 and the servers associated withthe datacenter 1008 are configured to connect to, or communicate via, anetwork 1006. In some implementations, a client 1004 associated with theuser 1002 can connect to the network 1006 via a communal connectionpoint, link, or path. In some implementations, a client 1004 associatedwith the user 1002 can connect to, or communicate via, the network 1006using a distinct connection point, link, or path. A connection point,link, or path can be wired, wireless, use other communicationstechnologies, or a combination thereof.

In some implementations, the network 1006 can include, for example, theInternet. In some implementations, the network 1006 can be, or include,a local area network (LAN), a wide area network (WAN), a virtual privatenetwork (VPN), or any other public or private means of electroniccomputer communication capable of transferring data between a client,such as the client 1004, and one or more servers associated with thedatacenter 1008, or a combination thereof. The network 1006, thedatacenter 1008, or any other element, or combination of elements, ofthe system 1000 can include network hardware such as routers, switches,load balancers, other network devices, or combinations thereof. Forexample, the datacenter 1008 can include a load balancer 1010 forrouting traffic from the network 1006 to various servers associated withthe datacenter 1008.

The load balancer 1010 can route, or direct, computing communicationtraffic, such as signals or messages, to respective elements of thedatacenter 1008. For example, the load balancer 1010 can operate as aproxy, or reverse proxy, for a service, such as an Internet-deliveredservice, provided by the datacenter 1008 to one or more remote clients,such as the client 1004, via the network 1006. Routing functions of theload balancer 1010 can be configured directly or via a Domain NameSystem (DNS). The load balancer 1010 can coordinate requests from remoteclients, such as the client 1004, and can simplify client access bymasking the internal configuration of the datacenter 1008 from theremote clients. Request coordination can include maintaining informationfor sessions, such as sticking sessions, between a client and a serviceor application provided by the datacenter 1008.

A load balancer 1010 can operate as a firewall, allowing or preventingcommunications based on configuration settings. Although the loadbalancer 1010 is depicted in FIG. 1 as being within the datacenter 1008,in some implementations, the load balancer 1010 can instead be locatedoutside of the datacenter 1008, for example, when providing globalrouting for multiple datacenters. In some implementations, loadbalancers can be included both within and outside of the datacenter1008.

In some implementations, the datacenter 1008 includes an applicationserver 1012 and a database server 1016. The application server 1012 orthe database server 1016 can be a computing system, which can includeone or more computing devices, such as a desktop computer, a servercomputer, or any other computer capable of operating as a server. Insome implementations, the application server 1012 or the database server1016 can be non-hardware servers implemented on a physical device, suchas a hardware server. In some implementations, the application server1012 and the database server 1016 can be implemented as a singlehardware server or as a single non-hardware server implemented on asingle hardware server. In some implementations, any number ofapplication servers or database servers can be implemented at thedatacenter 1008. In some implementations, the datacenter 1008 caninclude servers other than or in addition to the application server 1012or the database server 1016, for example, a web server.

In some implementations, the application server 1012 includes anapplication node 1014, which can be a process executed on theapplication server 1012. For example, and without limitation, theapplication node 1014 can be executed in order to deliver services to aclient, such as the client 1004, as part of a web application. Theapplication node 1014 can be implemented using processing threads,virtual machine instantiations, or other computing features of theapplication server 1012. In some implementations, the application node1014 can store, evaluate, or retrieve data from a database, such as thedatabase 1018 of the database server 1016.

In some implementations, the application server 1012 can include anysuitable number of application nodes, depending upon a system load orother characteristics associated with the application server 1012. Forexample, and without limitation, the application server 1012 can includetwo or more nodes forming a node cluster. In some implementations, theapplication nodes implemented on a single application server 1012 canrun on different hardware servers.

The database server 1016 can be configured to store, manage, orotherwise provide data for delivering services to the client 1004 over anetwork. In some implementations, the database server 1016 includes adata storage unit, such as a database 1018, which can be accessible byan application executed on the application node 1014. In someimplementations, the database 1018 can be implemented as a relationaldatabase management system (RDBMS), an object database, an XML database,a management information base (MIB), one or more flat files, othersuitable non-transient storage mechanisms, or a combination thereof.While limited examples are described, the database 1018 can beconfigured as or comprise any suitable database type. Further, thesystem 1000 can include one, two, three, or any suitable number ofdatabases configured as or comprising any suitable database type orcombination thereof.

In some implementations, one or more databases (e.g., the database1018), tables, other suitable information sources, or portions orcombinations thereof can be stored, managed, or otherwise provided byone or more of the elements of the system 1000 other than the databaseserver 1016, such as the client 1004 or the application server 1012.

Some or all of the systems and methods described herein can operate orbe executed on or by the servers associated with the system 1000. Forexample, an update for an application executed on the application node1014 can include updating or upgrading the database 1018. In someimplementations, the systems and methods described herein, portionsthereof, or combinations thereof can be implemented on a single device,such as a single server, or a combination of devices, for example, acombination of the client 1004, the application server 1012, and thedatabase server 1016.

In some implementations, the system 1000 can include devices other thanthe client 1004, the load balancer 1010, the application server 1012,and the database server 1016 as generally illustrated in FIG. 1. In someimplementations, one or more additional servers can operate as anelectronic computing and communications system infrastructure control,from which servers, clients, or both servers and clients, can bemonitored, controlled, configured, or a combination thereof.

In some implementations, the network 1006, one or more datacenters, suchas the datacenter 1008, and one or more load balancers, such as the loadbalancer 1010, can be implemented within a distributed computing system.In some implementations, a load balancer associated with a distributedcomputing system (e.g., the load balancer 1010) can communicate with thenetwork 1006, one or more datacenters (e.g., the datacenter 1008), otherload balancers, or a combination thereof. In some implementations, theload balancer 1010 can be configured to route communications to aprimary datacenter, identify a failover condition (e.g., such as anenumerated failover condition) at the primary datacenter, and redirectcommunications to a secondary datacenter until the failover condition isresolved. Although illustrated as a single unit in FIG. 1, a loadbalancer 1010 can be implemented as multiple physical or logical units.For example, a distributed computing system can include distinct routingunits, load balancing units, firewall units, or the like.

The primary datacenter can include a primary database, such as thedatabase 1018, and the secondary datacenter can include a secondarydatabase. In some implementations, the secondary database can include anexact or substantially exact mirror, copy, or replication of the primarydatabase. In some implementations, the primary database or the secondarydatabase can be implemented as a relational database management system(RDBMS), an object database, an XML database, one or more flat files, orthe like.

An application node implemented within a distributed computingenvironment can connect to or communicate with the primary database,which can be associated with the datacenter with which the applicationnode is associated, or associated with another datacenter. For example,a primary datacenter can include a primary database and a first set ofapplication nodes. A secondary datacenter can include a secondarydatabase and a second set of application nodes. The application nodes ofthe first and second sets can provide a service or application to remoteclients, and can read or write data in the primary database. Thesecondary database can mirror changes made to the primary database andprevent write operations from being performed directly on the secondarydatabase. In the event that a failover condition associated with theprimary database is identified, the secondary database can operate asthe primary database and can allow read or write access to data. Theprimary database can then operate as the secondary database, mirror thenew primary database, and prevent direct write access to the newsecondary database.

FIG. 2 generally illustrates a block diagram of an example internalconfiguration of a computing device 2000, such as a client 1004 or aserver, such as an application server 1012 or a database server 1016, ofthe system 1000 as generally illustrated in FIG. 1. As previouslydescribed, a client or server can be a computing system includingmultiple computing devices or a single computing device, such as amobile phone, a tablet computer, a laptop computer, a notebook computer,a desktop computer, a server computer, or other suitable computingdevices.

A computing device 2000 can include components or units, such as aprocessor 2002, a bus 2004, a memory 2006, peripherals 2014, a powersource 2016, a network communication unit 2018, a user interface 2020,other suitable components, or a combination thereof.

The processor 2002 can be a central processing unit (CPU), such as amicroprocessor, and can include single or multiple processors havingsingle or multiple processing cores. Alternatively, the processor 2002can include another type of device, or multiple devices, now-existing orhereafter developed, capable of manipulating or processing information.For example, the processor 2002 can include multiple processorsinterconnected in any manner, including hardwired or networked,including wirelessly networked. In some implementations, the operationsof the processor 2002 can be distributed across multiple physicaldevices or units that can be coupled directly or across a local area orother suitable type of network. In some implementations, the processor2002 can include a cache, or cache memory, for local storage ofoperating data or instructions.

In some implementations, the memory 2006 can include volatile memory,non-volatile memory, or a combination thereof. For example, the memory2006 can include volatile memory, such as one or more DRAM modules suchas DDR SDRAM, and non-volatile memory, such as a disk drive, a solidstate drive, flash memory, Phase-Change Memory (PCM), or any form ofnon-volatile memory capable of persistent electronic informationstorage, such as in the absence of an active power supply. In someimplementations, the memory 2006 can include another type of device, ormultiple devices, now-existing or hereafter developed, capable ofstoring data or instructions for processing by the processor 2002. Theprocessor 2002 can access or manipulate data in the memory 2006 via thebus 2004. Although shown as a single block in FIG. 2, the memory 2006can be implemented as multiple units. For example, a computing device2000 can include volatile memory, such as RAM, and persistent memory,such as a hard drive or other storage. Although depicted here as asingle bus, the bus 2004 can be composed of multiple buses, which can beconnected to one another through various bridges, controllers, oradapters.

The memory 2006 can include executable instructions 2008, data, such asapplication data 2010, an operating system 2012, or a combinationthereof, for immediate access by the processor 2002. The executableinstructions 2008 can include, for example, one or more applicationprograms, which can be loaded or copied, in whole or in part, fromnon-volatile memory to volatile memory to be executed by the processor2002. The executable instructions 2008 can be organized intoprogrammable modules or algorithms, functional programs, codes, codesegments, or combinations thereof to perform various functions describedherein. For example, the executable instructions 2008 can includeinstructions to provide enterprise information management, as describedabove. The application data 2010 can include, for example, user files,database catalogs or dictionaries, configuration information orfunctional programs, such as a web browser, a web server, a databaseserver, or a combination thereof. The operating system 2012 can be, forexample, Microsoft Windows®, Mac OS X®, or Linux®; or an operatingsystem for a small device, such as a smartphone or tablet device; or anoperating system for a large device, such as a mainframe computer. Thememory 2006 can comprise one or more devices and can utilize one or moretypes of storage, such as solid state or magnetic storage. The memory2006 can be distributed across multiple clients or servers, such asnetwork-based memory or memory in multiple clients or servers performingthe operations of clients or servers.

The peripherals 2014 can be coupled to the processor 2002 via the bus2004. The peripherals can be sensors or detectors, or devices containingany number of sensors or detectors, which can monitor the computingdevice 2000 itself or the environment around the computing device 2000.For example, a computing device 2000 can contain a geospatial locationidentification unit, such as a global positioning system (GPS) locationunit. As another example, a computing device 2000 can contain atemperature sensor for measuring temperatures of components of thecomputing device 2000, such as the processor 2002. Other sensors ordetectors can be used with the computing device 2000, as can becontemplated. In some implementations, the power source 2016 can be abattery, and the computing device 2000 can operate independently of anexternal power distribution system. Any of the components of thecomputing device 2000, such as the peripherals 2014 or the power source2016, can communicate with the processor 2002 via the bus 2004. In someimplementations, a client or server can omit the peripherals 2014. Theoperations of the processor 2002 can be distributed across multipleclients or servers, which can be coupled directly or across a local areaor other suitable type of network.

The network communication unit 2018 can also be coupled to the processor2002 via the bus 2004. In some implementations, the networkcommunication unit 2018 can comprise one or more transceivers. Thenetwork communication unit 2018 can, for example, provide a connectionor link to a network, such as the network 1006, via a network interface,which can be a wired network interface, such as Ethernet, or a wirelessnetwork interface. For example, the computing device 2000 cancommunicate with other devices via the network communication unit 2018and the network interface using one or more network protocols, such asEthernet, TCP, IP, power line communication (PLC), WiFi, infrared, GPRS,GSM, CDMA, or other suitable protocols.

A user interface 2020 can include a display; a positional input device,such as a mouse, touchpad, touchscreen, or the like; a keyboard; orother suitable human or machine interface devices. The user interface2020 can be coupled to the processor 2002 via the bus 2004. Otherinterface devices that permit a user to program or otherwise use thecomputing device 2000 can be provided in addition to or as analternative to a display. In some implementations, the user interface2020 can include a display, which can be a liquid crystal display (LCD),a cathode-ray tube (CRT), a light emitting diode (LED) display (e.g., anOLED display), or other suitable display.

As described, an application node, such as the application node 1014 canbe executed to deliver services to the user 1002, the client 1004, thecomponents of the datacenter 1008, or a combination thereof. In someimplementations, the application node 1014 is configured to perform,when executed by a processor, such as the processor 2002, an enterpriseinformation management application (“EIM application”).

In some embodiments, the EIM application may be configured to generatehierarchical data structures on information received from a user of theEIM system 1000. The EIM application may be executed on a servercomputing device, such as a server instance of the computing device2000. The hierarchical data structures represent enterprise informationcorresponding to various assets and liabilities of an organizationutilizing the EIM system 1000. A hierarchical data structure may includeone or more collection data objects. A collection data object mayrepresent physical “real-world” information about an asset or liability.For example, the user of the EIM system 1000 may include a knowledgeworker, such as attorney, accountant, property manager, asset manager,administrative assistant, an organizational member (e.g., in the case ofa family office, an organizational member may include a family member),or other suitable knowledge worker. The user may have special knowledgeof a particular asset or liability. For example, the user may be areal-estate attorney having special knowledge of a property asset,including the physical location and size of the property, the value ofthe property, tax implications of owning the property, otherinformation, or a combination thereof.

The user may input the information using the user interface 2020, asdescribed. The EIM application generates a first collection data objectusing the information provided by the user. The first collection dataobject represents the information of the property.

The hierarchical data structure may mimic how professionals operatingwithin the enterprise information management office think, plan, and/oroversee the organization's assets and/or liabilities. In someembodiments, each collection data object is a separate controlenvironment that allows its operations to be customized to meet itsspecific needs.

With reference to FIG. 3, an output interface 100 associated with theEIM system 1000 generally illustrates various information associatedused to generate corresponding collection data objects. In someembodiments, the output interface 100 may be displayed on a clientcomputing device, such as a client instance of the computing device2000. A two-tiered typing system may be configured to order thecollection data objects based on the subject matter type and/orownership of the real-world asset and/or liability represented by arespective collection data object. This may provide a significantimprovement over the use of simple electronic folder structures thatprovide a one-way linear organization and limit ordering to folder name,date added, etc. The two-tiered system for organizing collection dataobjects may allow related assets to be grouped together at the top ofthe hierarchy. For example, in the case of a family office, thetwo-tiered system of organizing collection data objects may allowcollection data objects representing revocable trusts to be groupedtogether.

In the example generally illustrated in FIG. 3, a top of the hierarchaldata structure may represent higher levels of owner and/or settlorcontrol above lessor levels of owner and/or settlor control. Forexample, in the case of a family office, LLCs, partnerships, andcorporations associated with the family may be organized and displayedat or near the top of the output interface 100. Conversely, irrevocabletrusts associated with the family may be organized below the LLCs,partnerships, and corporations associated with the family because thesettlor of an irrevocable trust has relinquished control throughcompleted gift or transfer of asset relative to assets contributed intoLLCs, partnerships, and corporations associated with the family.Further, irrevocable trusts may be organized by grantor and non-grantorattributes associated with the irrevocable trusts. Additionally, oralternatively, charitable organizations associated with the family mayappear at or near the bottom of the output interface 100.

The output interface 100 may include a first column and a second column.The first column may display all people and entities associated with theorganization's assets and/or liabilities. The second column may displayasset and liability collection data objects. In some embodiments, theoutput interface 100 may include additional or fewer columns thanillustrated in FIG. 3.

For example, the output interface 100 may include a fourth column thatmay display assets and liabilities collection data objects ordered ororganized from liquid to illiquid assets as they would appear on afinancial statement (e.g., with assets and cash near the top of thestatement, followed by real-estate, and then liabilities near the bottomof the statement), with each asset and liability collection locatedunder respective individual owners, joint owners, and/or entities.Further, the collection data objects may be organized in the fourthcolumn using any suitable organization.

Collection data objects that represent assets and liabilities heldindividually (e.g., by a single member of the organization) are placedunder respective organizational member identifiers in the outputinterface 100. This may allow users viewing the output interface 100 toquickly assess a scope of taxable estates and/or potential liabilitycoverage needs of the organization. Similarly, collection data objectsrepresenting assets and/or liabilities that are held jointly by morethan one member of the organization (e.g., having joint ownership), suchas, a married couple, tenants in common, or other joint ownership, aredistinguished on the output interface 100 by type as an untimely deathof one of the join owners could result in an unintended inheritance bysurvivorship or an asset interest passing through probate or other legalfunction.

The EIM system 1000 and the EIM application provide visibility and issuespotting of assets and liabilities associated with the organizationusing the hierarchical data structure, described, that is typically onlyavailable using manually produced diagrams, spreadsheets, and/or inseparate mind mapping type applications. The EIM system 1000 and the EIMapplication are configured to collectively manage and report on thesecomplex visibility and issue spotting requirements in a simple to reviewoutput interface, such as the output interface 100. It should beunderstood that information displayed in the respective columnsdescribed above may be displayed in columns other than is indicatedherein.

The respective collection data objects may be dynamically updated and/orconfigured by the EIM application. For example, as users of the EIMapplication operate to manage the enterprise information of theorganization, the users may provide updated information associated withrespective collection data objects., The EIM application is configuredto update respective collection data objects based on the updatedinformation. This may allow users to continuously reflect, via thecollection data objects, current subject matter and/or ownership of thereal-world assets or liabilities represented by respective collectiondata objects, and display the current state of the real-world assets orliabilities dynamically on the output interface 100. For example, as anasset or liability is sold or disposed of, its respective collectiondata object can be marked inactive on the output interface 100 based oninformation the user provides to the EIM application.

Inactive collection data objects remain in a menu bar associated withthe output interface 100 but appear in a sub-list below activecollection data objects on the output interface 100. In someembodiments, contents and/or information associated with inactivecollection data objects remain accessible by users of the EIM system1000 for reference to without having to wait for physical filespertaining to the inactive asset or liability represented by theinactive collection data object to delivered from storage or forarchived files to be made available. For example, a user may interactwith various menus, dropdown lists, and/or buttons on the outputinterface 100 in order to review active and/or inactive collection dataobjects. In some embodiments, collection data objects can be relocatedwithin the hierarchical data structure. For example, if firstorganizational member transfers an asset owned by the firstorganizational member to a second organizational member, a user canprovide the change in ownership to the EIM application. The EIMapplication may then update the respective collection data objectrepresenting the asset to reflect the ownership change.

Collection data objects may be “stacked” on the output interface 100 toreflect ownership. For example, in the case of a family office, anirrevocable trust that wholly owns two Regional LLC's, each of whichhold 2 local LLC's, each of which hold a cash account, parcel of realestate, and a commercial mortgage requires 19 collection data objects isgenerally illustrated on the output interface 100. Accordingly, the EIMsystem 1000 and the EIM application do not impose a limit on collectiondata object stacking as is generally illustrated in FIG. 3.

FIG. 4 generally illustrates a user control interface 200. The usercontrol interface 200 provide an interface for assigning access tocollection data objects by selecting (by a user) a box on a first sideof the user control interface 200. In some embodiments, the first sideof the user control interface 200 may be on the left side of the usercontrol interface 200. The user control interface 200 may provide aninterface for setting permissions to conduct activity separately forindividual smart data objects, as will be described, on a second side ofthe user control interface 200. In some embodiments, the second side ofthe user control interface 200 may be on the right side of the usercontrol interface 200.

The EIM application is configured to provide governance to eachrespective collection data object. For example, the EIM application mayinclude contact information stored in a contact table within a database,such as the database 1018. The contact information may include contactname, information related to the position of the contact within theorganization, a contact role, contact permissions, access rights (e.g.,information indicating what type of data objects and/or what time ofinformation associated with the data objects the user associated withthe contact information has rights to access, as will be explained),other suitable contact information, or a combination thereof. Thecontact information may be populated and/or stored in the contact tableby a user of the EIM system 1000 and/or imported from other suitablesystems, such as, an email system. In some embodiments, contactinformation may include contact information for a business, trust,philanthropic organization, or other group or organization. Further, auser may include an individual user or a business, organization,philanthropic organization, or other group of individuals.

As described, the user may select one or more contacts to associate witha respective collection data object. The EIM application receives theuser selection and associates the one or more selected contacts with therespective collection data object. In some embodiments, the EIMapplication generates an output or output information, such as using theoutput interface 100, that illustrates information associated with oneor collection data objects based on contact information associated witha user attempting to access the information associated with the one ormore collection data objects. For example, a user may attempt to view,via the output interface 100, information associated with one or morecollection data objects that user is associated with. The EIMapplication may identify a contact in the contact table that correspondsto the user. The EIM application may generate the output based on thecontact information associated with the user. For example, in the caseof a family office, the contact information for a user may indicate thatthe user is a family member. The family member may be associated withone or more collection data objects that represent one or morecorresponding assets owned or partially owned by the user.

The EIM application generates an output that includes the collectiondata objects associated with the user. By allowing access to collectiondata objects and associated smart data objects based on the contactinformation, a user with limited access relative to the entireorganization can locate and operate within collection data objects andsmart data objects using the appropriate requisite permissions (e.g.,determined based on their contact information) in order to complete theduties of the role in an independent and autonomous fashion. That is, alimited user can access what is required of the limited user's rolewithout violated security and permissions of the data objects. Thisallows for independent work by lower level users while maintaining alldocuments and items regardless of specific permissions in one system.

In some embodiments, the EIM application may configure the informationincluded in the output based on the user contact information. Forexample, in the case of a family office, when the user contactinformation indicates that the user is a family member, the EIMapplication includes in the output information about the ownership of anasset and/or liability associated with a collection data object, variousreports associated with an asset and/or liability associated with acollection data object, other suitable information, or a combinationthereof. In this case, the output may include a subset of allinformation associated with the collection data objects being displayedIn another example, the user contact information may indicate that theuse is a trustee responsible for the one or more collection dataobjects. The EIM application may include in the output upcoming actionitems, tasks, meetings, reports, ownership information, other suitableinformation, or a combination thereof. That is, the EIM application mayrestrict, limit, expand, or otherwise configure information included inthe output corresponding to the one or more collection data objectsbased on the user contact information. For example, the EIM applicationmay include in the output a subset of all information associated withthe collection data objects or all information associated with thecollection data objects. This allows for information to be kept privateand controlled, such that, only authorized users can see and/or interactwith information corresponding to their authorization (e.g., contactinformation).

In some embodiments, the user control interface 200 may include acollections details panel. The collections details panel may includeinformation associated with a collection data object. For example, thecollections details panel may include social security numbers associatedwith one or more users associated with a collection data object, one ormore account numbers associated with a collection data object, fundstransfer instructions (e.g., such as money wiring instructions)associated with a collection data object, other suitable information,and/or a combination thereof. As described, user contact informationindicates a level of privacy and confidentiality associated with foreach user allowing access into collection data objects based on theirneed to know and participation basis. By restricting users, activity,and/or information at the boundary line of each collection data object,common privacy violations are prevented. For example, common privacyviolations, such as inadvertently selecting the wrong auto-populatedrecipient in an email and/or curious staff browsing through paper orserver files may be prevented. The EIM application is configured torestrict permitted collection data object users to only communicatingand sharing information with other permitted collection data objectusers. Administrative rights are required to add user contactinformation, change user contact information permissions, and to removea user contact access.

FIG. 5 generally illustrates a collection data object dashboard 300 ofwith the EIM system 1000. In some embodiments, the collection dataobject dashboard 300 may provide improved visibility and access toinformation associated with the collection data objects than istypically possible using other systems. The collection data objectdashboard 300 displays all users, activity and information in ameaningful format. The collection data object dashboard 300 contains adetails panel, an activity section with separate tabs listing complianceservices being rendered, tasks as a record for day-to-day functions andoperations, events for upcoming meetings, other suitable information, ora combination thereof. A separate section on the collection data objectdashboard 300 may include a document library. In some embodiments, foreach collection data object, users can communicate create and/or storedocuments, conduct administrative activity relating to day-to-day tasks,record professional services rendered, complete recurring complianceresponsibilities, and/or document meetings and events using smart dataobjects, as will be described.

The collection data object dashboard 300 may be configured to displaypending activity associated with one or more collection data objects.Filters for each activity type allow users to locate: their completedwork, all completed tasks, compliance and meetings by user, and/or dateor service category. The document library list defaults to display, bythe EIM application on the output interface 100, ordering a last indocument at or near the top of the collection data object dashboard 300.This allows users to quickly scan the top of the document librarysection for recently received information. A document filter is alsoavailable to quickly navigate to any document by category or date.

The detail panel may include and/or display information thatnecessitates increased security control and therefore requirespermission for rights to view. As described, the EIM application isconfigured to display on the details panel information to a user basedon the user's contact information. The details panel may include three,or more or less, tabs. The first tab provides a section where users caninclude short descriptions about a person, entity, asset, or liabilitythat the collection data object is associated with. Information such aslegal name, legal situs, formation (birth) date, name and legal capacityof decision makers, stakeholders, agents and their contact information,tax identification numbers, tax filing requirements, etc. is allcritical to the governance of the collection data object. Thisinformation must be aggregated from multiple sources. For example, thevarious information described may be stored in one or more tables on oneor more databases. Further, the databases may be stored on one or moreservers, as described. In some embodiments, the information may bestored in a single database using multiple tables. The information maybe linked as related between the multiple tables.

A second tab displays a list of users who have access to participate inand/or view information associated with the collection data object. Thethird tab lists all activity within the collection data object. Thethird tab is configured to display, by user, all activity, informationstored and shared with respect to the collection data object such that afactual digital record is automatically captured eliminating the needfor fiduciary recordkeeping as a separate manual task. Additionally, oralternatively, the collection details panel allows a new sub-collectiondata object to be added below the collection dashboard panel beingviewed. The sub-collection data object may represent an asset orliability that is associated with the collection data object and ishierarchically below the collection data object. For example, thecollection data object may represent an LLC and the sub-collection dataobject may represent an asset owned by the LLC. In some embodiments, thecollection data object details panel includes a collection title, type,and location. The collection title, type, and location may be updated(e.g., changed or marked as inactive, for example) by a user. In someembodiments, the EIM application is configured to generate an annuallyrecurring compliance responsibility for each collection data objectgenerated by the EIM application. As is generally illustrated in FIG. 5,the annually recurring compliance responsibility is automaticallyimposed and has an initial due date 10 days after the collection dataobject is generated to insure annual collection data object reviews.While the due date can be amended, the default imposition of thecompliance responsibility is a system fail safe preventing new mattersfrom being neglected.

After the hierarchy data structure is established, users may utilizeinformation on their desk and/or focus on defining and applying thecollection data object's required governance, operations, compliance,and reporting responsibilities. In some embodiments, a secured detailspanel provides a notes section where users can indicate the collectiondata object's business purpose, tax filing status, account numbers, andpersonal preferences of owners and beneficiaries, and so on. In someembodiments, a compliance section allows all recurring responsibilitiesto be digitally generated using the EIM application's default compliancetemplates.

In some embodiments, the EIM application may track day-to-day operationswith task and event features of the collection data object dashboard300. All required documents are uploaded into the document library.Users communicate with one another in context of any compliance, task,event, or document. As work is completed, the collection data object'sactivity is captured to produce a fiduciary record to defend againstlegal and tax challenges and to inform successors with quick transparentvisibility into where the predecessor work ended and their work maybegin. The EIM application's compliance prompts professionals to conductan annual review of each collection data object to insure sufficiency ofits operational plan. The collection data object dashboard 300 maydisplay a comprehensive view all activity and information of eachseparate collection data object.

In some embodiments, the EIM application is configured to generate smartdata objects based on input information received from a user. Smart dataobjects may represent information associated with tasks, compliance,events, documents, other suitable information, or a combination thereof.For example, a user may input information associated with a meetingbetween the user and another user associated with the collection dataobject. The EIM application generates a smart data object using theinformation to represent the meeting. The smart data object ishierarchically below the collection data object, such that, the smartdata object may inherit attributes of the collection data object. Forexample, a user having access to the collection data object may alsohave access to the smart data object. By removing the need to specifyaccess and permissions at the smart data object level (e.g., because thesmart data objects inherit access and permissions from the correspondingcollection data objects), users generating the smart data objects savevalue time and limit potential mistakes by allowing inappropriate accessand permissions to be set at a smart data object level. This isespecially beneficial to large organizations utilizing the enterpriseinformation management office. Further, the user has more control overchanging access and permissions for an entire hierarchical structure(e.g., a collection data object and its associated smart data objects)by changing access and permissions at the collection data object level.In some embodiments, the attributes of the smart data object may beselectively modified by a user. For example, the user providing theinformation used to generate the smart data object may specify a list ofusers, using corresponding contact information, that can view and/orinteract with the smart data object. The list of users may be a subsetor different from the list of users that can view and/or interact withthe collection data object. As described, the EIM application maygenerate an output of information associated with one or more collectiondata objects based on the contact information of a user attempting toaccess the one or more collection data objects. Similarly, the EIMapplication generates output of the information associated with smartdata objects associated with the one or more collection data objectsbased on the user contact information. As described, the outputinformation may include a subset of all information associated with thesmart data objects or all information associated with the smart dataobjects based on the user contact information (e.g., access rightsindicated by the contact information as described).

In some embodiments, the EIM application stores a relationship and/orrelationship information between a collection data object and associatedsmart data objects in a data object relationship table of a database,such as the database 1018. For example, the EIM application may store inthe relationship table information indicating that a first collectiondata object is associated with a first smart data object and a secondsmart data object. Further, the EIM application may store in therelationship table information indicating that the first data object isassociated with the first collection data object and that a third smartdata object is associated with the first smart data object (e.g., thethird smart data object is a smart data object that is hierarchicallylower than the first smart data object). Additionally, or alternatively,the EIM application may store other suitable information in therelationship table than that described herein.

Smart data objects represent various suitable types of activities andinformation storage needed by the enterprise information managementoffice to effectively conduct operations, reporting, compliance, othersuitable functions, or a combination thereof of the organization usingthe enterprise information management office.

In some embodiments, the EIM application does not provide systemdefaults granting users permissions to view, add, modify, or remove thesmart data objects. For example, each user's permissions must bespecifically granted when the smart data object is generated. Forexample, the user providing the information that the EIM applicationuses to generate the smart data object may include with the informationcontact information for users permitted to view, add, modify, or removethe smart data object. This allows granular levels of security controlover activity and information represented by the smart data objectallowing each user to work as indicated by the contact informationassociated with the user without compromising privacy and/or security.For example, a clerk can file documents in collection data objects usinga smart data object without viewing the specific strategic activity andinformation reflected in the collection data object's other smart dataobjects. Additionally, or alternatively, a user may be restricted toadding a document, while not being permitted to view any otherdocuments.

In some embodiments, a user may use various templates that guide theuser through the various data rules associated with smart data objectsin order to provide appropriate information to the EIM application togenerate respective smart data objects. Every smart data object assignedto at least one collection data object by the EIM application based onthe information received from the user. Once initially assigned, a smartdata object may also be assigned, by the EIM application using theinformation received from the user, to other collection data objects.The user selects, from the input interface, a smart data object categoryand date. The selections govern storage of the smart data object withinthe collection data object, which in turn governs security.

In some embodiments, a smart data object may be initiated from a userdashboard, a document tab, a task tab, a compliance tab, an event tab,or other suitable tab. A smart data object can be added to anycollection data object that the user has access and permission withinthe hierarchical data structure. For example, when the smart data objectis initiated from a specific collection data object dashboard, such asthe collection data object dashboard 300, any features allowing smartdata objects to be added only permit the user to assign to a collectiondata object being viewed, which is auto-selected in the template. Fromthe details page of any smart data object, any attempts to link anothersmart data object are limited to the smart data objects assigned to thecollection data object of the original smart data object which isauto-selected for the user.

Smart data objects may be assigned to collection data objects and/orother smart data objects, as described, and/or linked to other smartdata objects. The EIM application uses a set of rules that govern theassignment and linking of a smart data object to another smart dataobject. This assignment and linking is required to facilitate assetand/or liability transfers or common activity between collection dataobjects. There is no limit to the number of collection data objectssmart data object can be assigned or linked to. However, access to viewsmart data objects are still governed by collection data objectsassociated with the smart data object.

FIG. 6 is a block diagram illustrating smart data object linking. A task402 is assigned to a collection 404, a collection 406, and linked to adocument 408, and a document 410. The document 408 may be assigned tocollection 404 and document 410 may be assigned to collection 406. Allpermitted users in Collections 404 and 406 will be able to view the task402 as it is assigned to both collections. While not all users may beable to access document 408 and 410. Smart data object permissioncontrols allow organizational leaders and professionals to be fullyinformed, conduct activity, and communicate while still restrictinginformation on a need to know basis.

Each smart data object facilities its own contextual communication withusers permitted within the collection data object the smart data objectis assigned to. Communications are restricted to its collection dataobjects users which eliminates the risk of inadvertently sending anemail to the wrong recipient.

Because collection data objects support both activity, (e.g.,operations, reporting compliance) and information management (e.g.,documents and communication), separate category systems are available todistinguish these different functions. For activity, collection dataobjects may include service categories which utilize terminology usersuse to describe services rendered. Service categories are particularlyhelpful for managing enterprise information management office activity.Filters for tasks, compliance and meetings all allow for this subjectmatter type filtering using service categories.

Collection data objects may also include data categories that use commonterminology for describing the various documents related toorganizational assets and/or liabilities. Data categories permit usersto search for specific common documents across the entire enterpriseinformation management office. Further, when users review status of, forexample, delivery of tax records to outside CPA's, the user can filterby service category to determine organizational wide compliance and whathas been completed or what is still pending. Additionally, oralternatively, if all of a particular type of document need to bereviewed, a data category associated with that type of document would beused to filter and locate for all organization members within theenterprise information management office. Additionally, oralternatively, if a status of a document is being reviewed by a user, aservice category associated with the document would be used to determinestatus and sufficiency of the document. The use of separate categoriessystems for services and information allow users to work, determinestatus of service commitments, and find information using their ownlanguage. For documents, the EIM application includes, with smart dataobjects representing the documents, data categories to identifydocuments by subject matter, limiting the list to universal terms withgoal of filtering to a navigable list.

In some embodiments, and as described, smart data objects allow forrecording and tracking of various enterprise information managementoffice functions. From a compliance perspective, enterprise informationmanagement offices must honor the individual compliance requirements ofevery existing entity, asset and liability that is a part of and/orassociated with the organization. While at first glance these compliancerequirements appear mundane as they are set and rarely change, withouttechnology to support their internal control processes, dailyoperational demands cause compliance work to oftentimes be postponed,sometimes forgotten or simply not recorded in a way that will beavailable to the next successor. Compliance risk for organizations canlie latent for decades. If records aren't available, the organizationwill face the associated risk if record support is not available.

The EIM application includes a compliance component The compliancecomponent is configured to assist enterprise information managementoffices customize the compliance needs on a collection data object basisfor every entity, asset and liability representing by a collection dataobject, so that each occurrence of every separate complianceresponsibility is established step by step; scheduled by step; assigned,conducted, recorded by step and reviewed by occurrence. As each step ofa compliance responsibilities become due, a compliance occurrence smartdata object, generated using information received from a user and/orobtained by the EIM application from other suitable sources, allows theuser responsible for the compliance occurrence to communicate, referencesource documents, document decisions, exceptions and authorization, andupload and link final work product for review. As users review work foraccuracy and sufficiency all communications and information are at theirfingertips, contextual and chronological so a minimum amount of time isrequired for review.

The EIM application generates compliance smart data objects to includeseparate sub-records for each occurrence, whether daily, weekly,monthly, quarterly, or annually, for each year it remains in effect.Since each occurrence is a separate sub-record, in response to an auditor challenge, enterprise information management offices can immediatelyaccess and provide exactly the period or occurrence in question. Many ofthe compliance smart data objects include generational timelines. It islikely during the lifetime of that compliance responsibility there willbe a regulatory, tax, legal or organizational member change thatrequires one or more steps to be amended. Compliance smart data objectsare configured such that all its specific features to be edited.However, the edits will only be applied to open occurrences, leaving anycompleted occurrence record unaltered for record preservation purposes.This allows each occurrence to properly document its known governance atthe time of its completion. The ability to edit compliance smart dataobjects is also helpful during staff transitions. The compliance smartdata object can be edited and reassigned to the new staff member. Allactivity completed by the former employer remains under their user nameand designation for identification purposes. Their prior communicationsand work is available with a single click for reference and training.

The EIM application utilizes default best practice compliance templatesstored in a best practices table of a database. The EIM application usesthe templates to apply the best practices to any collection data objectwhich can then be customized to meet the needs and objectives of itscollection. Compliance smart data objects are extremely flexible as theycan be single or multi-step. Each step is assigned to a specificpermitted user and given a due date; compliance instructions, linkedgoverning documents, and steps can be added or removed, reassigned,rescheduled, or other suitable functions. However, any edit only affectsopen occurrences; for each occurrence, a complete history is availableto support its completion; compliance filters allow staff to determinetheir open work; managers can review all compliance activity for status,and sufficiency for assurances. Also, all recurring work can beassessed, for consistency, productivity, workloads, assessment for newhires, and a basis for calculating expense or fees; attorneys candirectly review they compliance for the complex wealth strategies theydrafted rather than sending annual letters requesting updates and recordfor the various compliance duties; work can be outsourced but tightlycontrolled; external independent audits can be conducted without anydisturbance or interruption of family office staff. An auditor can beissued a user access and permission login to work from his office.

In some embodiments, the EIM application generates a user dashboardfilter which allows users a quick method of filtering tasks, compliance,and events represented by smart data objects that are assigned to and/orincludes the user.

In some embodiments, the EIM application generates collection dashboardfilters that sort all pending or completed smart data objects assignedto the collection data object being viewed with or without itssub-collection data objects and all smart data objects, pending orcompleted, with or without sub-collection data objects.

In some embodiments, the EIM application generates a documents tabfilter that allows user to sort all documents, represented by smart dataobjects, assigned to collection data objects that user has permission toview which helpful for finding common documents across multiplecollection data objects. A compliance tab filter allows the user to sortall open or completed compliance, represented by smart data objects,that the user has permission to view which is very helpful formanagement review of status, productivity, consistency among multipleusers, sufficiency, or other suitable information. A complete list ofcompliance can be generated which is a useful basis for evaluating costsor staffing needs. A tasks tab filter allows the user to sort all openor completed compliance, represented by smart data objects assigned tocollection data objects that the user has permission to view. A completelist of tasks, open or completed, can be generated. Since tasks are dayto day activities that were not anticipated, this list is helpful todetermine level of work by member, advisor, or other suitable role. Anevents tab filter allows the user to sort all open or completedcompliance, represented by smart data objects assigned to collectiondata objects that the user has permission to view.

FIGS. 7-27 generally illustrate a use case reflecting a typicalintra-family transaction that illustrates the activity and informationmanagement capabilities of the smart data objects. The EIM application,executed by the EIM system 1000 is configured to perform the stepsdescribed herein. The example illustrated in FIGS. 7-27 is forillustrative purposes only and merely represents one of a plurality ofscenarios that the EIM application and EIM system 1000 are configured toexecute.

FIG. 7 generally illustrates a step 1 a. In step 1 a a Family OfficeManager receives a call from his client, John Russell, regarding thesale of an asset (collection data object A-2) owned in his revocabletrust (collection data object A-1) to his family's dynasty trust(collection data object B-1), where John is the Grantor. John and theTrustee have agreed on the sale and want the family office to make ithappen in 3-5 days. This transaction arose from a discussion of what todo with the excess cash held in the Dynasty trust brokerage account(collection data object B-1) that was recently received from the sale ofanother trust asset. The Trust's excess cash needs to be invested andthe asset proposed for sale is suitable and was independently appraisedwithin the last few months which would provide a valid basis forestablishing a sales price.

FIG. 8 generally illustrates a step 1 b, step 1 c, and step 1 d. Step 1b FO Manager locates and reviews the asset's independent appraisal (DocA-1) referenced by John. Step 1 c FO Manager next navigates to theRussell Family Dynasty Trust (collection data object B-1) to review thetrust agreement (Doc-B-1) to determine the trustee's responsibility andauthority to invest and the most recent trust accounting (Doc B-1) toverify the excess cash position. Since the Family Office (“FO”) providesfiduciary administrative support to the Trustee, and to John as Trusteeof his Revocable Trust, the FO will represent both the buyer and sellerin this transaction. Step 1 d the information reviewed by the FO Manageris sufficient to reasonably proceed. Consistent with FO policies forrecordkeeping, the FO Manager creates a new collection data object, asdescribed above, (collection data object B-2) in the Dynasty Trust torecord the due diligence of the proposed asset and record the intentionsand actions of the Trustee.

FIG. 9 generally illustrates a step 1 e and step 1 f. Step 1 e fromJohn's asset Collection Dashboard (collection data object A-2), FOManager adds a new Task “Facilitate Sales Transaction” to initiate andtrack this transaction and selects the Service Category of “InvestmentOversight”. Since the FO is representing both the buyer and seller, thenew Task is assigned to both collection data object A-2 and collectiondata object B-2, to record how it independently oversaw this transactionon behalf of each party. When a Task is assigned to two Collection AllDocuments stored in each Collection's library are available for linking.All Users who are permitted Users in both Collections will see allactivity and documents linked from both Collections. Users who are onlya permitted User in one Collection, are limited to viewing only activityand documents linked from their permitted Collection For Task AB-1, anyUsers that John has permitted in his Collection A-2 who are not apermitted User by the Trustee of the Dynasty Trust will not see andTrust documents or Trust activity to maintain the privacy of the Trust'srecords while allowing substantial convenience and efficiency for the FOProfessionals who are rendering services to both John and the Trustee.

Step 1 f FO Manager next links the Appraisal (Doc A-1) and the TrustAccounting (Doc B-1) to Task AB-1 to facilitate the Sales Transaction.

FIG. 10 generally illustrates a step 1 g and a step 2 a. Step 1 g Withinthe Sales Task AB-1, the FO Manager emails Anthony Comm AB-1 asking himto schedule a conference call with attorney and CPA to discuss the salesstrategy.

Step 2 a Anthony receives the message in his email account, selects thequick link that navigates directly to Task AB-1 details page.

From Task AB-1, Anthony adds an Event AB-1 for the date and time of thetelephone conference with call in instructions. The new Event templateallows Anthony to provide a title and to select a category “investmentOversight.”

Since the users will be discussing the transaction from the perspectiveof the seller and buyer, the Event is assigned to both collection dataobjects, allowing all users from each assigned collection data object tobe invited. After saving Event AB-1 is created and all invited userswill receive an invitation in their email and upon acceptance, the Eventwill sync with the user's desktop calendar.

FIG. 11 generally illustrates a step 2 b. Anthony reviews Event AB-1details page and verifies that it is linked to the Task AB-1 from whichit was created. To double check that he added the Event to the correcttask, Anthony navigates through the link back to the Task AB-1.

The EIM application uniquely allows activities such as Tasks, Events andCompliance to be linked (as smart data objects) along with any requiredDocuments to automatically create a dynamic digital record.

Step 2 b Knowing that the FO's policy is to link all documents (usingsmart data objects) that are required for review or discussion during anEvent, Anthony locates the documents (e.g., using smart data objectsrepresenting the documents) referenced in his instructions and linksthem, using the input interface, to the Event.

FIG. 12 generally illustrates a step 3 a and a step 3 b. When a userneeds a document that is not assigned to one of the assigned libraries,its absence should alert users that the desired document may not havebeen properly filed. The user should use the Document tab and Documentfilter to locate the desired document and correct any collection dataobject assignments that had previously been omitted. The Document Taballows a user to view and search for all Documents in the System thatuser has permissions to view, irrespective of collection data objectassignment. Additionally, or alternatively, its absence would alert theuser that another collection data object should be assigned in order tolink the required Document, using a respective smart data object, whichis the case in the use case described herein. Anthony may realize thatboth the Trust Accounting and Trust Accounting (Doc B-1) are properlyfiled at the entity level. Since the Trustee's duties and the Trustassets are being discussed during the call, Anthony edits the Event toalso assign it to collection data object B-2.

In step 3 a, as is generally illustrated in FIG. 12, after the telephonecall, FO Manager enters all discussion notes in the comment section ofthe Event and sends an update to the client John and to the Trusteerequesting their confirmation to proceed with retaining counsel to draftthe required legal documents.

Step 3 b After FO Manager received confirmation from John and theTrustee to proceed, FO Manager adds a new Task AB-2 from the event AB-1to reflect the family office's retention of Attorney, on behalf of Buyerand Seller, and categorizes it as a “Legal Support Service.”

The Service Category “Legal Support Services” allows family offices tofilter all collection data objects to determine number and status ofpending and closing legal matters.

FIG. 13 generally illustrates FO manager adding another Task AB-2 fromEvent AB-1 to reflect the buyer and seller's retention of Attorney todraft the sales agreement.

FIG. 14 generally illustrates a step 4. At step 4. Step 4 FO Managerneeds to add another Task B-1 to the Event that only pertains to thebuyer which is the Dynasty Trust. The attorney will prepare a Resolutiondocumenting the basis for suitability and the Trustee's exercise ofdiscretion to purchase the trust investment. The Dynasty Trust Agreement(Doc B-2) is linked to record which version was in effect and reliedupon at the time of the exercise of discretion to purchase. The documentlink also serves as a quick reference for the attorney to review theTrust's investment standard.

Since Task B-1 is only assigned to collection data object B-1 andcollection data object B-2, any user of collection data object A-1 orcollection data object B-1, who is not a User of collection data objectB-1 and collection data object B-2 will be not be able to view Task B-1in the Linked Items list of Event AB-1.

FIG. 15 generally illustrates a step 5 and a step 6. Step 5 AfterAttorney has drafted the Trustee Resolution, he logs into the EIMapplication using the client 1004, as described, and immediately on hisDashboard sees the link to Task B-1 which he selects to conveniently andsecurely upload the new trust resolution Doc B-3 and to provide a copyto the Trustee for review.

Step 6 Later, Attorney completed the draft of the sales agreement (DocAB-2), he uploads it to the Task AB-2 and notifies the Trustee and theFO Manager.

FIG. 16 generally illustrates a step 7, a step 8, and a step 9. Step 7After the Trustee reviews and signs the Trust Resolution (Doc B-3) hereplies to Attorney and FO Manager. Likewise, Trustee reviews and signsthe Sales Agreement (Doc AB-2) and replies to authorize the Attorney andFO Manager to proceed with closing the sale once John's signature hasbeen obtained.

Step 8: From Task AB-2, FO Manager emails John, letting him know thatthe Trustee has signed the Sales Agreement (Doc AB-2) and that hisreview and signature will allow the FO to proceed with closing thetransaction.

Step 9 John reviews the Sales Agreement (Doc AB-2), signs and replies toFO Manager to move forward.

FIG. 17 generally illustrates a step 10 and a step 11. Step 10 From TaskAB-1, the FO Manager attached the executed Sales Agreement to Task AB-1and adds a Comment to Anthony requested that he initiate a wire from theTrust Brokerage collection data object B-1 to the Seller's accountcollection data object A-1, as designated in the Sales Agreement andmarks the Comment private so that only the Link is visible in Anthony'semail.

Step 11 After Anthony completes the wire request (Doc BA-4), he uploadsa copy and links it 1) to collection data object B-1 brokerage accountfrom which the funds are drawn, 2) collection data object A-1 where theseller's funds are deposited 3) collection data object A-2, as for taxrecords for the sale 4) and then to the Trust's new asset collectiondata object B-2 as the record of tax basis and source of funds topurchase the asset.

In the Comment section of the Task AB-1, Anthony replies to the FOManager, the Trustee and John confirmation that the wire has beeninitiated, and likewise marks the Comment as private.

FIG. 18 generally illustrates a step 12. Step 12 Later, Anthony laterreceives an email from collection data object A-1, CS Brokerage firm,confirming their receipt and deposit of wired funds. Anthony copies thebrokerage firm email and paste's it into the comment section of TaskAB-1 as a final record that the exchange of funds is complete.

FIG. 19 generally illustrates a step 13. Step 13 FO Manager receives anInvoice from Attorney for services rendered for Task B-1. From the TaskB-1 details page, FO Manager uploads the Invoice (Doc B-5) and adds aComment and sends it to Controller noting that the invoice is approvedfor payment.

When adding a new document from a Task, Event or Compliance DetailsPage, the EIM application automatically adds it to the collection dataobject that the Task (e.g., represented by a smart data object) isassigned to as a convenience for Users.

FIG. 20 generally illustrates a step 14. Step 14 Controller receivesemail that links to Task B-1 to review Legal invoice (Doc B-5) andissues payment from Trust collection data object B-1. Controller thenselects the Doc B-5 link to add a note on the Document that payment hasbeen processed and the check number.

Add payment details to the Invoice Documents rather than on the Taskdetails page, allows anyone reviewing office wide invoices with quickreference of processing.

Controller “Edits” Doc B-5 to assign the Invoice to account from whichfunds were drawn to pay the Invoice which was the ABC Brokeragecollection data object B-1. This allows Doc B-5 to be included in theBrokerage account's document library so the bookkeeper will be verifyingsource documents for all trust disbursements during the reconciliationprocess.

FIG. 21 generally illustrates a step 15 and a step 16. Step 15 SinceTask B-1 seems to be complete, FO Manager proceeds with the final reviewto insure all information reviewed by the Trustee and Attorney is linkedor described in the comments. Finding everything in order, FO Managermarks the Trust Task B-1 complete so that the family office's pendinglegal matters stays current.

Step 16 Likewise, FO Manager completes a final review of the Task AB-2,verifying that the executed Sales Agreement is attached, attorneyinvoice and record of payment are all linked and then marks Task AB-2complete.

FIG. 22 generally illustrates a step 17. Step 17 From Task AB-1, FOManager notifies the LLC Manager Ron Meyer of the percentage sale to anew LLC Member and notes that the linked Sales Agreement contains therequired language assigning the 20% of John's interest to the Trust.

FO Manager also requests that Ron provide any documents that need to besigned by the new member and that Form K-1's and Financials be provideddirectly to the Trust in the EIM system 1000, as with other members.

FIG. 23 generally illustrates a step 18. Step 18 From Task AB-1, FOManager selects the Sales Agreement (Doc AB-2) and then selects “AddItem” to create a new Task A-1 Titled “Reconcile Asset Post Closing,”and assigns the new Task A-1 to the family office accountant and selects“Reconciliation Services” as the Service Category. FO manager alsoattaches the Wire Request reflecting the date, amount and depositaccount of the sales proceed for verification.

The Service Category “Reconciliation Services” allows the FO to trackprogress of on the timely production of FO Financial Statements acrossall entities.

FIG. 24 generally illustrates a step 19. Step 19 To Task AB-1, Ron Meyeruploads the Amendment to the Operating Agreement that the Trustee needsto sign as a new member and requests that the FO Manager obtain thesignature of the Trustee. FO Manager notes that Ron improperly uploadedthe Document (e.g., using a smart data object representing the documentand linked to a collection data object). Since the Task AB-1 is assignedto two collection data objects but the new document only pertains to theTrust collection data object, FO Manager Edits the Document so that itis only assigned to collection data object B-2.

FIGS. 25-27 generally illustrates a step 20. Step 20 Knowing that whencollection data object B-2 was recently created which automaticallytriggers the application of a Review Compliance template that must becompleted within 10 days, FO Manager navigates to collection data objectB-2 and locates Compliance B-1 that is pending and assigned to her toconduct the initial review of the yearly Review Compliance record.

FIG. 28 is a flow diagram of a process 3000 for managing enterpriseinformation according to the principles of the present disclosure. At3002, the process 3000 receives first input information. For example,the EIM application receives, as described, input information from auser using an input interface. In some embodiments, the input interfacemay be accessed by the user using a client computing device, such as aclient instance of the computing device 2000. The input interface, viathe client computing device, may be configured to communicateinformation received from the user to the EIM application, beingexecuted on a server computing device, as described. The inputinformation may be associated with a first feature of an organization.For example, the input information may represent real-worldcharacteristics of the first feature of the organization. At 3004, theprocess 3000 generates a first data object using the first inputinformation. For example, the EIM application, as described, generates afirst collection data object based on the first input information. Thefirst collection data object represents the real-world characteristicsof the first feature.

At 3006, the process 3000 generates a second data object using secondinput information. For example, the EIM application, as described, mayreceive information from the user associated with a task, even,document, compliance, or other suitable information associated with thefirst collection data object. The EIM application generates a smart dataobject using the second input information. At 3008, the process 3000associates the second data object with the first data object. Forexample, the EIM application, as described, may hierarchically associatethe second data object with the first data object using the first inputinformation and/or the second input information.

At 3010, the process 3000 generates output information based on usercontact information. For example, the EIM application, as describedgenerates output information based on the contact information associatedwith the user attempting to access the first data object and/or thesecond data object. The output information may represent portions of thefirst data object and the second data object that the user, according tothe contact information, has permission to view and/or interact with. At3012, the process 3000 displays the output information. For example, theEIM application, as described, may use a suitable display to display theoutput information. The output information may be displayed using theoutput interface 100, as described.

In some embodiments, a method for enterprise information managementincludes receiving, at a server computing device, first inputinformation, from a first user using a client computing device, thatcorresponds to a first identifying a first feature of an organization.The method further includes generating, by the server computing deviceand using the input information, a first data object that represents thefirst feature of the organization. The method further includesgenerating, by the server computing device, a second data object basedon second input information. The method further includes hierarchicallyassociating, by the server computing device, the second data object withthe first data object using the first input information and the secondinput information. The method further includes storing, by the servercomputing device, a relationship between the first data object and thesecond data object in a first database. The method further includesgenerating, by the server computing device output information, inresponse to a second user accessing the first data object, based on thefirst data object, the second data object, and contact informationassociated with the second user and retrieved from a second databaseseparate from the first database, wherein the output informationincludes a subset of information indicated by the first data object andthe second data object, the subset of information being determined basedon access rights indicated by the contact information. The methodfurther includes displaying, on the client computing device, the outputinformation on a display.

In some embodiments, the first data object represents at least onephysical attribute of the first feature of the organization. In someembodiments, the first data object represents owner informationassociated with the first feature of the organization. In someembodiments, the first feature of the organization includes an asset ofthe organization. In some embodiments, the first feature of theorganization includes a liability of the organization. In someembodiments, the second data object represents a document associatedwith the first feature of the organization. In some embodiments, thesecond data object represents a task associated with the first featureof the organization.

In some embodiments, system for enterprise information managementincludes a memory and a processor, wherein the memory includesinstructions executable by the processor to: receive first inputinformation, from a first user, that corresponds to a first identifyinga first feature of an organization; generate, using the inputinformation, a first data object that represents the first feature ofthe organization; generate a second data object based on second inputinformation; hierarchically associate the second data object with thefirst data object using the first input information and the second inputinformation; generate output information, in response to a second useraccessing the first data object, based on the first data object, thesecond data object, and contact information associated with the seconduser; and display the output information on a display.

In some embodiments, the first data object represents at least onephysical attribute of the first feature of the organization. In someembodiments, the first data object represents owner informationassociated with the first feature of the organization. In someembodiments, the first feature of the organization includes an asset ofthe organization. In some embodiments, the first feature of theorganization includes a liability of the organization. In someembodiments, the second data object represents a document associatedwith the first feature of the organization. In some embodiments, thesecond data object represents a task associated with the first featureof the organization.

Some embodiments, according to the principles of the present disclosure,include, a non-transitory computer-readable storage medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: receiving first inputinformation, from a first user, that corresponds to a first identifyinga first feature of an organization; generating, using the inputinformation, a first data object that represents the first feature ofthe organization; generating a second data object based on second inputinformation; hierarchically associating the second data object with thefirst data object using the first input information and the second inputinformation; generating output information, in response to a second useraccessing the first data object, based on the first data object, thesecond data object, and contact information associated with the seconduser; and displaying the output information on a display.

In some embodiments, the first data object represents at least onephysical attribute of the first feature of the organization. In someembodiments, the first data object represents owner informationassociated with the first feature of the organization. In someembodiments, the first feature of the organization includes an asset ofthe organization. In some embodiments, the first feature of theorganization includes a liability of the organization. In someembodiments, the second data object represents a document associatedwith the first feature of the organization. In some embodiments, thesecond data object represents a task associated with the first featureof the organization.

The word “example” is used herein to mean serving as an example,instance, or illustration. Any aspect or design described herein as“example” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the word“example” is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X includes A or B” is intended to mean any of thenatural inclusive permutations. That is, if X includes A; X includes B;or X includes both A and B, then “X includes A or B” is satisfied underany of the foregoing instances. In addition, the articles “a” and “an”as used in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form. Moreover, use of the term “animplementation” or “one implementation” throughout is not intended tomean the same embodiment or implementation unless described as such.

Implementations of the transmitting station 102 and/or the receivingstation 106 (and the algorithms, methods, instructions, etc., storedthereon and/or executed thereby) can be realized in hardware, software,or any combination thereof. The hardware can include, for example,computers, intellectual property (IP) cores, application-specificintegrated circuits (ASICs), programmable logic arrays, opticalprocessors, programmable logic controllers, microcode, microcontrollers,servers, microprocessors, digital signal processors or any othersuitable circuit. In the claims, the term “processor” should beunderstood as encompassing any of the foregoing hardware, either singlyor in combination. The terms “signal” and “data” are usedinterchangeably. Further, portions of the transmitting station 102 andthe receiving station 106 do not necessarily have to be implemented inthe same manner.

Further, in one aspect, for example, the transmitting station 102 or thereceiving station 106 can be implemented using a general-purposecomputer or general-purpose processor with a computer program that, whenexecuted, carries out any of the respective methods, algorithms and/orinstructions described herein. In addition, or alternatively, forexample, a special purpose computer/processor can be utilized which cancontain other hardware for carrying out any of the methods, algorithms,or instructions described herein.

Further, all or a portion of implementations of the present disclosurecan take the form of a computer program product accessible from, forexample, a computer-usable or computer-readable medium. Acomputer-usable or computer-readable medium can be any device that can,for example, tangibly contain, store, communicate, or transport theprogram for use by or in connection with any processor. The medium canbe, for example, an electronic, magnetic, optical, electromagnetic, or asemiconductor device. Other suitable mediums are also available.

The above-described embodiments, implementations and aspects have beendescribed in order to allow easy understanding of the present inventionand do not limit the present invention. On the contrary, the inventionis intended to cover various modifications and equivalent arrangementsincluded within the scope of the appended claims, which scope is to beaccorded the broadest interpretation so as to encompass all suchmodifications and equivalent structure as is permitted under the law.

What is claimed is: A method for enterprise information management,comprising: receiving, by a server computing device, first inputinformation, from a first user using a client computing device, thatcorresponds to a first identifying a first feature of an organization;generating, by the server computing device and using the inputinformation, a first data object that represents the first feature ofthe organization; generating, by the server computing device, a seconddata object based on second input information; hierarchicallyassociating, by the server computing device, the second data object withthe first data object using the first input information and the secondinput information; storing, by the server computing device, arelationship between the first data object and the second data object ina first database; generating, by the server computing device, outputinformation, in response to a second user accessing the first dataobject, based on the first data object, the second data object, andcontact information associated with the second user and retrieved from asecond database separate from the first database, wherein the outputinformation includes a subset of information indicated by the first dataobject and the second data object, the subset of information beingdetermined based on access rights indicated by the contact information;and displaying, on the client computing device, the output informationon a display.
 2. The method of claim 1, wherein the first data objectrepresents at least one physical attribute of the first feature of theorganization.
 3. The method of claim 1, wherein the first data objectrepresents owner information associated with the first feature of theorganization.
 4. The method of claim 1, wherein the first feature of theorganization includes an asset of the organization.
 5. The method ofclaim 1, wherein the first feature of the organization includes aliability of the organization.
 6. The method of claim 1, wherein thesecond data object represents a document associated with the firstfeature of the organization.
 7. The method of claim 1, wherein thesecond data object represents a task associated with the first featureof the organization.
 8. A system for enterprise information management,comprising: a memory; and a processor, wherein the memory includesinstructions executable by the processor to: receive first inputinformation, from a first user, that corresponds to a first identifyinga first feature of an organization; generate, using the inputinformation, a first data object that represents the first feature ofthe organization; generate a second data object based on second inputinformation; hierarchically associate the second data object with thefirst data object using the first input information and the second inputinformation; storing, by the server computing device, a relationshipbetween the first data object and the second data object in a firstdatabase; generating, by the server computing device, outputinformation, in response to a second user accessing the first dataobject, based on the first data object, the second data object, andcontact information associated with the second user and retrieved from asecond database separate from the first database, wherein the outputinformation includes a subset of information indicated by the first dataobject and the second data object, the subset of information beingdetermined based on access rights indicated by the contact information;and display the output information on a display.
 9. The system of claim8, wherein the first data object represents at least one physicalattribute of the first feature of the organization.
 10. The system ofclaim 8, wherein the first data object represents owner informationassociated with the first feature of the organization.
 11. The system ofclaim 8, wherein the first feature of the organization includes an assetof the organization.
 12. The system of claim 8, wherein the firstfeature of the organization includes a liability of the organization.13. The system of claim 8, wherein the second data object represents adocument associated with the first feature of the organization.
 14. Thesystem of claim 8, wherein the second data object represents a taskassociated with the first feature of the organization.
 15. Anon-transitory computer-readable storage medium, comprising executableinstructions that, when executed by a processor, facilitate performanceof operations, comprising: receiving first input information, from afirst user, that corresponds to a first identifying a first feature ofan organization; generating, using the input information, a first dataobject that represents the first feature of the organization; generatinga second data object based on second input information; hierarchicallyassociating the second data object with the first data object using thefirst input information and the second input information; storing, bythe server computing device, a relationship between the first dataobject and the second data object in a first database; generating, bythe server computing device, output information, in response to a seconduser accessing the first data object, based on the first data object,the second data object, and contact information associated with thesecond user and retrieved from a second database separate from the firstdatabase, wherein the output information includes a subset ofinformation indicated by the first data object and the second dataobject, the subset of information being determined based on accessrights indicated by the contact information; and displaying the outputinformation on a display.
 16. The non-transitory computer-readablestorage medium of claim 15, wherein the first data object represents atleast one physical attribute of the first feature of the organization.17. The non-transitory computer-readable storage medium of claim 15,wherein the first data object represents owner information associatedwith the first feature of the organization.
 18. The non-transitorycomputer-readable storage medium of claim 15, wherein the first featureof the organization includes an asset of the organization.
 19. Thenon-transitory computer-readable storage medium of claim 15, wherein thefirst feature of the organization includes a liability of theorganization.
 20. The non-transitory computer-readable storage medium ofclaim 15, wherein the second data object represents a documentassociated with the first feature of the organization.